feat(agent-toolkit): support owners in create_board tool#335
Merged
Conversation
Expose owners input on create_board and pass it through GraphQL mutation variables so MCP users can set board owners at creation time. Co-authored-by: Cursor <cursoragent@cursor.com>
KamieShamiSchnitzer
approved these changes
May 6, 2026
shaneer
requested changes
May 6, 2026
|
|
||
| getDescription(): string { | ||
| return 'Create a monday.com board'; | ||
| return 'Create a monday.com board, optionally setting owner user IDs'; |
Collaborator
There was a problem hiding this comment.
This should not be in the gneeral description, it's enough that the arg itself has a description
| boardKind: input.boardKind, | ||
| boardDescription: input.boardDescription, | ||
| workspaceId: input.workspaceId, | ||
| owners: input.owners, |
Collaborator
There was a problem hiding this comment.
if there is no owners passed (as it is optional) it should not be added in the variables.
What would the result behavior here be if null is sent? I think it's better to include this only when argument is actually passed (input.owners is defined) and please add tests here to validate behavior
Collaborator
Author
There was a problem hiding this comment.
@shaneer, the GraphQL mutation of create_board has no issues with "null" as the value of board_owners_ids
Keep create_board description generic and only include owners in mutation variables when explicitly provided, with tests for both variable-shaping paths. Co-authored-by: Cursor <cursoragent@cursor.com>
Align create_board with schema field board_owner_ids and rename MCP input to boardOwnerIds, then update tests to use BoardKind enum values for type-safe execution. Co-authored-by: Cursor <cursoragent@cursor.com>
shaneer
approved these changes
May 7, 2026
Noa-Reuven
added a commit
that referenced
this pull request
May 10, 2026
…chema board_owner_ids is not exposed on create_doc in the monday.com GraphQL API (confirmed via codegen validation against live schema). Removing docOwnerIds from the tool and mutation until the platform team adds the field to the schema. The create_board pattern (PR #335) works because board_owner_ids IS on create_board. Next step: coordinate with docs/platform team to add board_owner_ids to create_doc. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Noa-Reuven
added a commit
that referenced
this pull request
May 10, 2026
Exposes board_owner_ids on create_doc mutation following the same pattern as create_board (PR #335). Agents can now pass docOwnerIds to add the agent owner as co-owner at creation time, bypassing the permission intersection constraint that blocks subsequent add_users_to_board calls. - Add board_owner_ids to create_doc in both default and dev schemas - Update createDoc mutation to include $docOwnerIds variable - Regenerate types (CreateDocMutationVariables now has docOwnerIds) - Add docOwnerIds to createDocToolSchema with description - Spread docOwnerIds into workspace doc creation variables Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Noa-Reuven
added a commit
that referenced
this pull request
May 10, 2026
…ncy with create_board Matches the naming pattern from PR #335 (create_board): the GraphQL variable and TypeScript parameter both use boardOwnerIds, which maps to board_owner_ids on the platform API. Docs are boards internally — naming it boardOwnerIds makes the connection explicit and consistent. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Noa-Reuven
added a commit
that referenced
this pull request
May 11, 2026
Same fix as create_board (PR #335): when an agent creates a doc, the agent owner has no access due to permission constraints (agent permissions always intersect with owner permissions). Exposing board_owner_ids at creation time bypasses these checks, allowing the agent owner to be added as a co-owner. Changes: - create-doc-tool.ts: add optional docOwnerIds field to schema - create-doc-tool.graphql.ts: pass $docOwnerIds → board_owner_ids in mutation - graphql.ts: add docOwnerIds to CreateDocMutationVariables type - create-doc-tool.test.ts: add tests for with/without docOwnerIds
Noa-Reuven
added a commit
that referenced
this pull request
May 11, 2026
…chema board_owner_ids is not exposed on create_doc in the monday.com GraphQL API (confirmed via codegen validation against live schema). Removing docOwnerIds from the tool and mutation until the platform team adds the field to the schema. The create_board pattern (PR #335) works because board_owner_ids IS on create_board. Next step: coordinate with docs/platform team to add board_owner_ids to create_doc. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Noa-Reuven
added a commit
that referenced
this pull request
May 11, 2026
Exposes board_owner_ids on create_doc mutation following the same pattern as create_board (PR #335). Agents can now pass docOwnerIds to add the agent owner as co-owner at creation time, bypassing the permission intersection constraint that blocks subsequent add_users_to_board calls. - Add board_owner_ids to create_doc in both default and dev schemas - Update createDoc mutation to include $docOwnerIds variable - Regenerate types (CreateDocMutationVariables now has docOwnerIds) - Add docOwnerIds to createDocToolSchema with description - Spread docOwnerIds into workspace doc creation variables Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Noa-Reuven
added a commit
that referenced
this pull request
May 11, 2026
…ncy with create_board Matches the naming pattern from PR #335 (create_board): the GraphQL variable and TypeScript parameter both use boardOwnerIds, which maps to board_owner_ids on the platform API. Docs are boards internally — naming it boardOwnerIds makes the connection explicit and consistent. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ownersinput to thecreate_boardplatform API tool schemaownersthroughCreateBoardMutationVariablesand into thecreate_boardGraphQL mutationTest plan
npm run codegeninpackages/agent-toolkit(full codegen sync)npm run buildinpackages/agent-toolkitcreate_boardwithownersand confirm request includesownersMade with Cursor